<h1>Help and Support</h1>
<p>Please submit bugs and feature requests <%= link_to "here", "http://code.google.com/p/iterationplanner/issues/list" , :popup => true %>. You need a gmail account to sign in.</p>

<h2><p><i>Some good practices when using this tool: </i></p></h2>
<b>Conventions used for specifying a 'Deliverable':</b>
<ul>
  <li>Project/Release Name: This field represents a release name to identify the release version. These could be codenames e.g. Intel's 'Conroe'. Or they could map to something like 2008Q1 or simply Version numbers.
  <li>Product Name: The name of the product. e.g 'iPhone'. This field is useful if same group of developers work on multiple product lines.
  <li>Feature Name: Specific feature of the specified produce. e.g 'Calendar Management'
  <li>Description: A brief description of what would be the output of this deliverable at the end of this iteration. e.g Implement.., Refactor.., Design.., Get requirements ..
  <li>Resources: People Responsible for the completion of the deliverable.
  <li>Comments: Any comments about this deliverable. A date/time + initial of who entered the comment is useful. If the deliverable is deferred or move to next iteration or cancelled a reason why that happened.
</ul>

<b>Before an iteration planning meeting</b>
<p>Everyone likes short and sweet meetings. Here is what you can do to help:
<ul>
  <li>Talk to your team members whom you plan to work with and decide what you will work on. 
  <li>Talk to your manager/supervisor if you need direction on project priorities, resources or time
  <li>Put those things in a todo list so that they can be efficiently be added to the next iteration in the meeting.
</ul>
<br />
<br />
<b><i>Some links on Agile Software:</i></b>

<ul>
  <li> <%= link_to "Manifesto for Agile Software Development", "http://agilemanifesto.org", :popup => true %>
</ul>

<br />
<br />
More to come....
